Should improve (I have added some logger info that it is still processing) #119 - not yet best user experience, but already better

It looks like the triggers are re-enable before the data is imported - the wizard is still open - see logging on screen shot.

@domi4484 Is this a similar error as you have found in TEKSI wastewater? https://github.com/teksi/wastewater/pull/211/files

How could the TEKSI improvment be backported to qgep?

@sjib Yes it seems similar. Basically you need to re-enable the triggers only after the dialog has been acceptedd/rejected.

By re-thinking on this we could have an issue (in TEKSI as well) if someone kills QGIS before the trigger are re-enabled they will remain disabled forever.
Maybe we should add a check on startup of the plugin or some other mechanism to check if the trigger are enabled

• Changed all post-processing to extra function qgep_postimport

With that the triggers are enabled after the import - this speeds up the import greatly (e.g. Testdata K from @urskaufmann in 3 minutes instead of 30 minutes or more).

This needs these datamodel changes 1.6.2 to work properly!

By re-thinking on this we could have an issue (in TEKSI as well) if someone kills QGIS before the trigger are re-enabled they will remain disabled forever.
@domi4484 Glad to have you're review on my work - may be you can add your suggestions for this also in this.

@ponceta Ready for review and then merging - needs these QGEP/datamodel#235 to work properly!